Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-72429

Option to Disable Smart Links For Non-Atlassian Products in ADF editor

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • Editor - Cloud
    • None
    • 452
    • 107
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Atlassian update - 06 October 2022

      Hey all!

      Thank you again for your patience and your contribution.

      Today is the day. We’re happy to share that our solution has just been released to all Jira and Confluence users!

      You are now able to

      • keep smart links as your default view, but add exceptions for the domains you want to insert as simple URLs instead (for example your dev/stage environments or third party tools you use that you’d rather see the URL for)
      • turn smart links off by default, but add exceptions for the domains you want to keep them for (for example Jira, Confluence, Google Drive or Figma)

      This is where your settings live → https://id.atlassian.com/manage-profile/link-preferences. You can also access the settings page by clicking your avatar at the top right of your product, clicking ‘Manage account’ and then heading to the ‘Link preferences’ tab. If you need more help, feel free to check out our step-by-step guide.

      While we are confident that this will satisfy the needs of most users, we do acknowledge that there is a need for a site-wide, admin-controlled setting as well. For everyone interested in that feature, please follow this new ticket: https://jira.atlassian.com/browse/JRACLOUD-79892 

      And last but not least, to all our loyal Trello users: while we haven’t finished the required work just yet, these settings will also work for your connected Trello accounts soon.

      Thank you again for participating.

      Andre | Product Manager, Linking Platform

       


      Hey everyone!

      Thank you all for your continuous feedback and your patience!

      We’re happy to share that we’ve made great progress on the proposed solution and feel confident to share some details of the feature and when you can expect it to be released.

      How will the feature work?

      • Users will be able to set their preferred view for all links to either URL, Inline, Card or Embed Smart Link view, with Inline being the default setting
      • Additionally users will be able to set their preferred views for specific domains/URLs
        • Example 1: you could choose URL view for a specific domain you don’t want to insert as smart links, but keep smart links on for all other URLs
        • Example 2: you could keep Smart Links for your Jira and Confluence links, default your Giphy and Youtube links to Embed, and default all other links to URL
      • When you set preferred views for specific domains/URLs, we can’t guarantee that your preferred view is always possible. While the ‘URL’ view will always be possible for links that match your exception, ‘Inline, ‘Card’ and ‘Embed’ will depend on whether or not we currently support the preferred view for that domain.
      • The feature will be found in a central place at https://id.atlassian.com/manage-profile/, affecting Smart Links in Jira, Confluence and Trello
        • Example 1: Your preferences will work for the Jira Description field, Confluence Pages and Trello Description field, because they all uses Smart Links
        • Example 2: Your preferences won’t work for the ‘Linked Issues’ feature on the Jira Issue View, because it’s not a Smart Link

      When will the feature be released?

      • You can expect this to be shipped to all users during the month of October

      Want to contribute?

      Have a good day everyone,

      Andre | Product Manager, Linking Platform


      Atlassian update - 02 May 2022

      Hey everyone!

      Thank you all for your valuable feedback, and special thanks to those who have reached out directly and participated in user testing sessions with us.

      I’m happy to announce that we going to provide you with the following solution:

      • Every user will be able to set 'URL’ as their default insertion format instead of the smart link format
      • Every user will be able to set this for either all non-Atlassian URLs, or only for specific domains, so that you have the option to continue using some smart links you find useful, but not others
      • This setting will overwrite the default insertion format, but still allows you to upgrade your links to smart links after you've inserted them
      • This setting will be effective across all Atlassian products you are authenticated with (e.g. Jira, Confluence, Trello).

      What are we not doing?

      • Admins will not yet be able to perform this setting for all their users. That’s because we want to respect the preference of each content creator. There's a related ticket on this request that you can follow and vote for.
      • Smart Links can’t be turned off from a reader's perspective - if the creator of a link inserted a link as a smart link, you will see it as a smart link. That’s because we want to respect content the way it was intended by the author.

      Some of you have raised concerns about the security and privacy of our smart links. When conducting our user research we found that in many cases that’s because users believe that when they connect their 3rd party account (e.g. Google Drive) it will also connect it for other users. It is important to understand that when you connect to a 3rd party app and authenticate with it, that connection exists for only you. So, if you authenticate with your 3rd party account (e.g. Google Drive) and insert a link, other users will not automatically be able see that link's information, unless they have also authenticated with the service themselves and have got the permissions required to see it.

      We hope that the proposed solution will make working with smart links easier for you, and we are looking forward to receiving your feedback.

      Andre | Product Manager, Linking Platform


      Atlassian update - 06 April 2022

      Hi everyone!

      We've been listening to your feedback, concerns and ideas to improve our Smart Link solution and realised that especially in recent months more and more users were unhappy with the feature. We appreciate all your feedback, and special thanks to those who have used the opportunity to book in with me, to help us understand the problems better so we can find the best solution.

      I'm happy to announce that we have prioritzed this issue and are going to work on a solution soon. You can expect an update with details about the solution by the end of April.

      Thank you again for your active contribution to help us make our products better!

      Andre | Product Manager, Linking Platform


      Hi all!

      We are currently looking into different solutions that can address the problems you are experiencing working with Smart Links.

      There are different reasons to why the current experience is not ideal for some of your use cases, and we want to make sure we are addressing the most pressing problems first. Some solutions require more time than others, and we want to make sure we can improve the experience incrementally while exploring further possibilities.

      I'm happy to announce that you will soon have the option to bypass the Smart Link experience using Cmd+Shift+V when inserting links. We are in the process of implementation and I will update you all once it's available to you.

      From the feedback we've received, we know that this will be helpful for many of you, although not the ideal solution for everyone - please know we will continue to explore further. We've received a lot of feedback on the experience of typing text that automatically turns into Smart Links (e.g. when typing file names, domain names or formats) - we will be exploring solutions for these use cases next.

      If you want to take a bigger role in helping us build better products, or just want some face-to-face time to express your ideas, please feel free to book in some time with me via https://calendly.com/andremauritz/smart-links-feedback.

      Thank you again for all your feedback.

      Andre | Product Manager, Linking Platform


      Hi folks! Just updating you that we have picked this up and have started implementing a solution, which should solve most of the problems mentioned here. Expect an update on this post in a couple of weeks.

      Cheers,
      Andre | Product Manager, Linking Platform


      Hi all! 
      A quick update from the Jira issue and Smart Links teams.

      Firstly, thanks for your ongoing, candid feedback. Please rest assured that we are closely monitoring your feedback and discussing internally. 

      I understand this issue is increasingly causing challenges for our users. I'm currently working with our Smart Links team to explore this problem space to better understand nearer term improvements. 

      I'll continue to update this ticket as I have more to share. 

      Cheers, 
      Venkatesh | Jira Issue PM


      Hi everyone,

      Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use Jira so we can continue improving your experience. We have reviewed this issue over the last few days, however there are not currently any plans to implement this suggestion.

      While we understand the logic for wanting to have different default options, our current focus is on making the unfurl states of Smart Links richer both inside and outside the editor across our products. Based off customer feedback, this is where we believe it’s most necessary to focus our efforts in the short-term.

      In the meantime, you can change the Smart Link back to a normal url by clicking on the Smart Link in edit mode, and selecting “Display URL” from the toolbar dropdown.

      We will continue to track this ticket and feedback across our various customer channels. Please remember that jira.atlassian.com is one of many inputs for the Jira roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Venkatesh Vasudevan
      vvasudevan@atlassian.com
      Product Manager, Jira Cloud

       

      Problem Definition

      On the new issue view, whenever you paste a link on the Description or comment field, Jira initiates a Smart Link that will attempt to preview this link. It shows the below link "Connect to preview link"

      Suggestion

      Allow an option to be able to disable the Smart link by providing a "turn off/on" Smart link button, either on the Instance as a whole or on per Issue basis.

      Workaround

      Note: Current workarounds only apply when creating a smart link. As a user viewing a smart link there is no current workaround.

      In order to remove the Smart link from rendering on the new issue view.

      • Paste the Google link for example, once it renders to preview the link
      • Press Ctrl + Z (Windows) or Cmd + Z (MacOS) (this will revert the link to a normal blue link)

      Alternative workaround:

      • When inserting the link, be sure to use http:// instead of [https://|https:]. The Smart Card feature will not be activated, and upon visiting the URL, it will automatically redirect to https:// for these services.

            [JRACLOUD-72429] Option to Disable Smart Links For Non-Atlassian Products in ADF editor

            Some really useful information and suggestions were deleted in the frenzy of hapless censorship. 

            > Only thing useful I've found so far is backtick'ing everything. It seems like that keeps it from getting messed with.

            > Slack does smart links right. It's your choice on whether to auto-unfurl, and you have the control to disable it "in future for this site" if you have it enabled by default - and MOST IMPORTANTLY - it doesn't REPLACE your content. It augments it. Think "showing a preview" if your content has a link to a image/webpage/etc.

            > 1) You should have immediately removed this feature.  It won't break anything.  I'm guessing that the majority of admins do not want this and won't miss it when it is gone. 
            > 2) Once you have figured out how to allow teams to enable this with appropriate controls, you could offer the option to re-enable it (or, given your track history, automatically re-enable it but then provide controls for us to turn it off again). 

            [SmartLinks...]
            > # Completely disregard all security and obfuscate all REAL URLs for the title of the final destination of the page (Just in case it might say "Never gonna give you up" (Which ironically is what they are doing with the URL, not giving it up)
            > # Make it completely impossible for anyone who does ANY type of SEO work and needs to see the URL
            > # Make it IMPOSSIBLE for any developer that works on LOCAL HOST, in a DEV, STAGE or PREPROD environment that uses a different structure than Production, which by my estimate is um... 99.9% of everyone.
            > # Make it as Painful as humanly possible for any Project Manager to understand and follow changes from one page to another.
            > # Make it IMPOSSIBLE to migrate any page and know which is which because both pages have the same Title
            > # Make it IMPOSSIBLE for developers that use Angular and have a new build with the base structure setup or any vanilla project starting out.

            > This [the "fix"] solves nothing from the admin perspective and added hundreds of hours in new additional training time to teach people how to make sure the tickets they make are readable for the dev team for literally NO REASON except Atlassian thinks its a good idea. I am completely boggled at why this issue has been so bungled. Hundreds of people have been crystal clear as to what is needed here: Make the URL style a default setting that admin can configure for their whole company.

            > What if our links are behind authentication?  If I am documenting a list of links behind authentication, ALL of the links show the same rich information making Jira useless.  

            > it attempts to change the names of python files to links, because ".py" is a tld

             

            Ryan Dasso added a comment - Some really useful information and suggestions were deleted in the frenzy of hapless censorship.  > Only thing useful I've found so far is backtick'ing everything. It seems like that keeps it from getting messed with. > Slack does smart links right. It's your choice on whether to auto-unfurl, and you have the control to disable it "in future for this site" if you have it enabled by default - and MOST IMPORTANTLY - it doesn't REPLACE your content. It augments it. Think "showing a preview" if your content has a link to a image/webpage/etc. > 1) You should have immediately removed this feature.  It won't break anything.  I'm guessing that the majority of admins do not want this and won't miss it when it is gone.  > 2) Once you have figured out how to allow teams to enable this with appropriate controls, you could offer the option to re-enable it (or, given your track history, automatically re-enable it but then provide controls for us to turn it off again).  [SmartLinks...] > # Completely disregard all security and obfuscate all REAL URLs for the title of the final destination of the page (Just in case it might say "Never gonna give you up" (Which ironically is what they are doing with the URL, not giving it up) > # Make it completely impossible for anyone who does ANY type of SEO work and needs to see the URL > # Make it IMPOSSIBLE for any developer that works on LOCAL HOST, in a DEV, STAGE or PREPROD environment that uses a different structure than Production, which by my estimate is um... 99.9% of everyone. > # Make it as Painful as humanly possible for any Project Manager to understand and follow changes from one page to another. > # Make it IMPOSSIBLE to migrate any page and know which is which because both pages have the same Title > # Make it IMPOSSIBLE for developers that use Angular and have a new build with the base structure setup or any vanilla project starting out. > This [the "fix"] solves nothing from the admin perspective and added hundreds of hours in new additional training time to teach people how to make sure the tickets they make are readable for the dev team for literally NO REASON except Atlassian thinks its a good idea. I am completely boggled at why this issue has been so bungled. Hundreds of people have been crystal clear as to what is needed here: Make the URL style a default setting that admin can configure for their whole company. > What if our links are behind authentication?  If I am documenting a list of links behind authentication, ALL of the links show the same rich information making Jira useless.   > it attempts to change the names of python files to links, because ".py" is a tld  

            Ryan Dasso added a comment -

            This issue needs to be re-opened, as it's still not fixed. SmartLinks are still a plague of inefficiency and harassment for users of the platform. You've completely wasted your efforts to keep the feature, as the only viable option is to completely remove SmartLinks. 

            Does Atlassian realize their platform sends an email to everyone subscribed to an issue when a comment is deleted? If you're going to be tyrants, at least do it right! You're not supposed to tell the peons when you're censoring them! If you're going to edit history, don't broadcast it to the world! You're not even good at being despicable. 

            Ryan Dasso added a comment - This issue needs to be re-opened, as it's still not fixed. SmartLinks are still a plague of inefficiency and harassment for users of the platform. You've completely wasted your efforts to keep the feature, as the only viable option is to completely remove SmartLinks.  Does Atlassian realize their platform sends an email to everyone subscribed to an issue when a comment is deleted? If you're going to be tyrants, at least do it right! You're not supposed to tell the peons when you're censoring them! If you're going to edit history, don't broadcast it to the world! You're not even good at being despicable. 

            I am also shocked at seeing that Atlassian employee Hana Ganesh is deleting useful historical comments from this ticket. *I am perplexed as to why they closed this request without effectively addressing the problem amid widespread user dissatisfaction with this feature. * People have hated this "enhancement" since the day it was introduced several years ago. I was mildly pleased they did not delete MY humble comment from AUG/11/2022. I must really be important....LOL

            "Please give us a way to disable this stupid smart links auto link creator. It is driving our users crazy ever since we upgraded from 8.8.0 to 8.15.1 a few months ago.

            When a user pastes text from windows notepad into the description field it turns their information into html drivel."

            David Redwine added a comment - I am also shocked at seeing that Atlassian employee Hana Ganesh is deleting useful historical comments from this ticket. *I am perplexed as to why they closed this request without effectively addressing the problem amid widespread user dissatisfaction with this feature. * People have hated this "enhancement" since the day it was introduced several years ago. I was mildly pleased they did not delete MY humble comment from AUG/11/2022. I must really be important....LOL "Please give us a way to disable this stupid smart links auto link creator. It is driving our users crazy ever since we upgraded from 8.8.0 to 8.15.1 a few months ago. When a user pastes text from windows notepad into the description field it turns their information into html drivel."

            Kyle W. added a comment -

            Kyle W. added a comment - Also look at https://jira.atlassian.com/browse/JRACLOUD-84313

            Kyle W. added a comment -

            This is not the only ticket that the user Hana Ganesh has deleted comments on.

            Kyle W. added a comment - This is not the only ticket that the user Hana Ganesh has deleted comments on.

            I was shocked to see the deluge of notifications from comments being deleted. If this was done by an Atlassian employee, that brings into SERIOUS doubt Atlassian's ethical standards. Comments (even critical ones) should not be modified or removed unless they are abusive, offensive, or contain private information.

            Mark Neidlinger added a comment - I was shocked to see the deluge of notifications from comments being deleted. If this was done by an Atlassian employee, that brings into SERIOUS doubt Atlassian's ethical standards. Comments (even critical ones) should not be modified or removed unless they are abusive, offensive, or contain private information.

            Today (11th December 2024) a user called Hana Ganesh, apparently an Atlassian employee, has started deleting comments for this issue that are critical of Atlassian's lack of response or plain indifference to the real pain that many Jira users felt because of this issue.  Far too many users, particularly organization-level customer Admins are frustrated and feel (quite rightly) as though their pleas for "sensible" features are ignored while Atlassian rolls out "fancy" features that (it seems) these users do not want. They just want Jira to work properly, and to have sane defaults, and to feel as though there was meaningful consultation with key end-users (like Admins) that have to deal with the fallout.

            If this is the best that Atlassian can do, i.e. "sanitizing" comments, then shame on Atlassian! It's time to start taking user feedback seriously or to lose even more customers who have reached their frustration limit.

            NOTE: The old comments can still be seen in the History.  And if they suddenly disappear, then it will show that there is "one set of features for Atlassian" and a different set for "ordinary" users who have been requesting the ability to remove accidentally-added private information from Jira issues that may have GDPR consequences.

            Jason Armistead added a comment - Today (11th December 2024) a user called Hana Ganesh, apparently an Atlassian employee, has started deleting comments for this issue that are critical of Atlassian's lack of response or plain indifference to the real pain that many Jira users felt because of this issue.  Far too many users, particularly organization-level customer Admins are frustrated and feel (quite rightly) as though their pleas for "sensible" features are ignored while Atlassian rolls out "fancy" features that (it seems) these users do not want. They just want Jira to work properly, and to have sane defaults, and to feel as though there was meaningful consultation with key end-users (like Admins) that have to deal with the fallout. If this is the best that Atlassian can do, i.e. "sanitizing" comments, then shame on Atlassian! It's time to start taking user feedback seriously or to lose even more customers who have reached their frustration limit. NOTE: The old comments can still be seen in the History.  And if they suddenly disappear, then it will show that there is "one set of features for Atlassian" and a different set for "ordinary" users who have been requesting the ability to remove accidentally-added private information from Jira issues that may have GDPR consequences.

            It’s really annoying that this feature is enabled by default. I understand that the developers want to create a wow effect for new users, but when you start making a table with many links, fixing it becomes a nightmare. It’s great that you can now disable this function, but each user has to do it individually – there’s still no overall configuration!

            Aleksandr Abashkin added a comment - It’s really annoying that this feature is enabled by default. I understand that the developers want to create a wow effect for new users, but when you start making a table with many links, fixing it becomes a nightmare. It’s great that you can now disable this function, but each user has to do it individually – there’s still no overall configuration!

            Kyle W. added a comment -

            So instead of doing what we ask as your customers, you do this junk instead?

             

            <--

            More detail in Smart Links with better features

            We've upgraded Smart Links to show the information you need with improved features to increase your productivity.

            The changes include modernised Inline, Card, Embed, and Hover display views with new layouts, shapes, colors, and fonts.

            To view these changes:

            1. Copy or type in a URL in a Jira comment or description.
            2. Select the link.
            3. Change how the link is displayed from the Smart Link toolbar.
            4. Select Save.
            5. Hover over the display and interact with link elements.

            -->

             

            How about you just let us disable them already?

            Kyle W. added a comment - So instead of doing what we ask as your customers, you do this junk instead?   <-- More detail in Smart Links with better features We've upgraded Smart Links to show the information you need with improved features to increase your productivity. The changes include modernised Inline, Card, Embed, and Hover display views with new layouts, shapes, colors, and fonts. To view these changes: Copy or type in a URL in a Jira comment or description. Select the link. Change how the link is displayed from the Smart Link toolbar. Select Save. Hover over the display and interact with link elements. -->   How about you just let us disable them already?

            At least you deliver something useful, not like this stubborn customer ignoring Atlassian. Thank you

            Sebastian Lutter added a comment - At least you deliver something useful, not like this stubborn customer ignoring Atlassian. Thank you

              c124c5bdcbf1 Andre Mauritz
              hnyeche Prince N
              Votes:
              1266 Vote for this issue
              Watchers:
              434 Start watching this issue

                Created:
                Updated:
                Resolved: